Medium access control interface to coordinate multi-site operation for 5g or other next generation wireless network

ABSTRACT

A system that facilitates monitoring communication between a network node device and a communication device, wherein information is communicated by utilizing a first distribution unit (DU) node device comprising a first medium access control (MAC) layer component of the network node device and receiving condition information representative of a condition, wherein the condition indicates whether to add a second DU node device comprising a second MAC layer component to be utilized by the communication device. In response to determining that the condition indicates addition of the second DU node device, facilitating establishing a connection between the first MAC layer component of the first DU node device and the second MAC layer component of the second DU node device using a MAC interface and facilitating communication of control plane information and user plane information between the first MAC layer component and the second MAC layer component using the MAC interface.

RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 17/089,405, filed Nov. 4,2020, which applications claim priority to U.S. Provisional PatentApplication No. 62/941,658, filed Nov. 27, 2019, and entitled “MEDIUMACCESS CONTROL INTERFACE TO COORDINATE MULTI-SITE OPERATION FOR 5G OROTHER NEXT GENERATION WIRELESS NETWORK”, the entireties of whichpriority applications are hereby incorporated by reference herein.

TECHNICAL FIELD

This disclosure relates generally to interface between medium accesscontrol layers of network node devices in wireless communication system.More specifically, facilitating establishing a medium access controlinterface to coordinate communication between distribution units, e.g.,for 5th generation (5G) or other next generation wireless network.

BACKGROUND

5G wireless systems represent a next major phase of mobiletelecommunications standards beyond the current telecommunicationsstandards of 4th generation (4G). In addition to faster peak Internetconnection speeds, 5G planning aims at higher capacity than current 4G,allowing a higher number of mobile broadband users per area unit, andallowing consumption of higher or unlimited data quantities. Currently,wireless specifications define various features such as multipletransmission and reception point (multi-TRP) enhancements, and carrieraggregation/dual connectivity (CA/DC) enhancements. For example, carrieraggregation (CA) across different component carriers could be supportedacross two different non-co-located network node devices (e.g., gNB orgNodeB) or gNB-distributed units (gNB-DU). Also, a user equipment (UE)could receive different spatial layers on the same component carrierfrom two non-co-located transmission and reception points (TRP).

The above-described background relating to multi-TRP and CA is merelyintended to provide a contextual overview of some current issues, and isnot intended to be exhaustive (e.g., although problems and solution aredirected to next generation networks such as 5G, the solutions can beapplied to 4G/LTE technologies). Other contextual information may becomefurther apparent upon review of the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system in which anetwork node device and user equipment (UE) can implement variousaspects and embodiments of the subject disclosure.

FIG. 2 illustrates a block diagram of an exemplary 5G networkarchitecture.

FIG. 3A illustrates an example of protocol functions for a gNB withCU-DU split architecture according to various aspects and embodimentsdescribed herein.

FIG. 3B illustrates an example of CU-DU split architecture according tovarious aspects and embodiments described herein.

FIG. 4A illustrates a block diagram of an example, non-limiting systemthat facilitates establishing a medium access control interface tocoordinate communication between distribution units in accordance withone or more embodiments described herein.

FIG. 4B illustrates a block diagram of an example, non-limiting systemthat facilitates establishing a medium access control interface tocoordinate communication between distribution units in accordance withone or more embodiments described herein.

FIG. 5 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein.

FIG. 6 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein.

FIG. 7 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein.

FIG. 8 illustrates an example block diagram of an example mobile handsetoperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein.

FIG. 9 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of various embodiments. One skilled inthe relevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor, a process running on a processor, an object, anexecutable, a program, a storage device, and/or a computer. By way ofillustration, an application running on a server and the server can be acomponent. One or more components can reside within a process, and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Further, these components can execute from various machine-readablemedia having various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, a local areanetwork, a wide area network, etc. with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

The words “exemplary” and/or “demonstrative” are used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive—in a manner similar to the term “comprising” as an opentransition word—without precluding any additional or other elements.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, or machine-readable media. Forexample, computer-readable media can include, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media.

As an overview, various embodiments are described herein to facilitateestablishing a medium access control interface to coordinatecommunication between distribution units. For simplicity of explanation,the methods (or algorithms) are depicted and described as a series ofacts. It is to be understood and appreciated that the variousembodiments are not limited by the acts illustrated and/or by the orderof acts. For example, acts can occur in various orders and/orconcurrently, and with other acts not presented or described herein.Furthermore, not all illustrated acts may be required to implement themethods. In addition, the methods could alternatively be represented asa series of interrelated states via a state diagram or events.Additionally, the methods described hereafter are capable of beingstored on an article of manufacture (e.g., a machine-readable storagemedium) to facilitate transporting and transferring such methodologiesto computers. The term article of manufacture, as used herein, isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media, including a non-transitorymachine-readable storage medium.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G, Universal MobileTelecommunications System (UMTS), and/or Long-Term Evolution (LTE), orother next generation networks, the disclosed aspects are not limited to5G, a UMTS implementation, and/or an LTE implementation as thetechniques can also be applied in 3G, 4G or other LTE systems. Forexample, aspects or features of the disclosed embodiments can beexploited in substantially any wireless communication technology. Suchwireless communication technologies can include UMTS, Code DivisionMultiple Access (CDMA), Wi-Fi, Worldwide Interoperability for MicrowaveAccess (WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS,Third Generation Partnership Project (3GPP), LTE, Third GenerationPartnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High SpeedPacket Access (HSPA), Evolved High Speed Packet Access (HSPA+),High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink PacketAccess (HSUPA), Zigbee, or another IEEE 802.XX technology. Additionally,substantially all aspects disclosed herein can be exploited in legacytelecommunication technologies.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate establishing amedium access control interface to coordinate communication betweendistribution units. Facilitating establishing a medium access controlinterface to coordinate communication between distribution units can beimplemented in connection with any type of device with a connection tothe communications network (e.g., a mobile handset, a computer, ahandheld device, etc.) any Internet of Things (IoT) device (e.g.,toaster, coffee maker, blinds, music players, speakers, etc.), and/orany connected vehicles (cars, airplanes, space rockets, and/or other atleast partially automated vehicles (e.g., drones)). In some embodimentsthe non-limiting term user equipment (UE) is used. It can refer to anytype of wireless device that communicates with a radio network node in acellular or mobile communication system. Examples of UE are targetdevice, device to device (D2D) UE, machine type UE or UE capable ofmachine to machine (M2M) communication, PDA, Tablet, mobile terminals,smart phone, laptop embedded equipped (LEE), laptop mounted equipment(LME), USB dongles, etc. Note that the terms element, elements andantenna ports can be interchangeably used but carry the same meaning inthis disclosure. The embodiments are applicable to single carrier aswell as to multicarrier (MC) or carrier aggregation (CA) operation ofthe UE. The term carrier aggregation (CA) is also called (e.g.,interchangeably called) “multi-carrier system”, “multi-cell operation”,“multi-carrier operation”, “multi-carrier” transmission and/orreception.

In some embodiments the non-limiting term radio, network node device, orsimply network node is used. It can refer to any type of network nodethat serves UE is connected to other network nodes or network elementsor any radio node from where UE receives a signal. Examples of radionetwork nodes are Node B, base station (BS), multi-standard radio (MSR)node such as MSR BS, evolved Node B (eNB or eNodeB), next generationNode B (gNB or gNodeB), network controller, radio network controller(RNC), base station controller (BSC), relay, donor node controllingrelay, base transceiver station (BTS), access point (AP), transmissionpoints, transmission nodes, remote radio unit (RRU), remote radio head(RRH), nodes in distributed antenna system (DAS), relay device, networknode, node device, etc.

Cloud radio access networks (RAN) can enable the implementation ofconcepts such as software-defined network (SDN) and network functionvirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controller(e.g., controller, central controller, or centralized unit) that cancontrol routing of traffic within the network and between the networkand traffic destinations. The SDN controller can be merged with the 5Gnetwork architecture to enable service deliveries via open applicationprogramming interfaces (“APIs”) and move the network core towards an allinternet protocol (“IP”), cloud based, and software driventelecommunications network. The SDN controller can work with or take theplace of policy and charging rules function (“PCRF”) network elements sothat policies such as quality of service and traffic management androuting can be synchronized and managed end to end.

According an embodiment, a system can comprise a processor and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations comprising monitoringcommunication between a network node device and a communication device,wherein information is communicated by utilizing a first distributionunit node device comprising a first medium access control layercomponent of the network node device and receiving condition informationrepresentative of a condition, wherein the condition indicates whetherto add a second distribution unit node device comprising a second mediumaccess control layer component to be utilized by the communicationdevice. The system can further facilitate in response to determiningthat the condition indicates addition of the second distribution unitnode device, facilitating establishing a connection between the firstmedium access control layer component of the first distribution unitnode device and the second medium access control layer component of thesecond distribution unit node device using a medium access controlinterface and facilitating communication of control plane informationand user plane information between the first medium access control layercomponent and the second medium access control layer component using themedium access control interface.

According to another embodiment, described herein is a method that cancomprise monitoring, by a device comprising a processor, communicationbetween a network node device and a communication device, whereininformation is communicated by utilizing a first distribution unit nodedevice comprising a first medium access control layer component of thenetwork node device. The method can further comprise receiving, by thedevice, a condition, wherein the condition indicates whether to add asecond distribution unit node device comprising a second medium accesscontrol layer component to be utilized by the communication device. Themethod can further in response to determining that the conditionindicates addition of the second distribution unit node device,facilitating, by the device, establishing a connection between the firstmedium access control layer component of the first distribution unitnode device and the second medium access control layer component of thesecond distribution unit node device using a medium access controlinterface and initiating, by the device, communication of control planeinformation and user plane information between the first medium accesscontrol layer component and the second medium access control layercomponent using the medium access control interface.

According to yet another embodiment, a device can comprise a processorand a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations comprisingmonitoring communication between a network node device and acommunication device, wherein information is communicated by utilizing afirst distribution unit node device of the network node devicecomprising a first medium access control layer component. The device canfurther comprise receiving a request to reconfigure radio resources,wherein the request to reconfigure the radio resources comprisesutilizing a second distribution unit node device comprising a secondmedium access control layer component. The device can further comprisein response to the receiving the request to reconfigure the radioresources, facilitating establishing a connection between the firstmedium access control layer component of the first distribution unitnode device and the second medium access control layer component of thesecond distribution unit node device using a medium access controlinterface and initiating communication of control plane information anduser plane information between the first medium access control layercomponent and the second medium access control layer component using themedium access control interface.

These and other embodiments or implementations are described in moredetail below with reference to the drawings. Repetitive description oflike elements employed in the figures and other embodiments describedherein is omitted for sake of brevity.

FIG. 1 illustrates a non-limiting example of a wireless communicationsystem 100 in accordance with various aspects and embodiments of thesubject disclosure. In one or more embodiments, system 100 can compriseone or more user equipment UEs 102. The non-limiting term user equipment(UE) can refer to any type of device that can communicate with a networknode in a cellular or mobile communication system. A UE can have one ormore antenna panels having vertical and horizontal elements. Examples ofa UE comprise a target device, device to device (D2D) UE, machine typeUE or UE capable of machine to machine (M2M) communications, personaldigital assistant (PDA), tablet, mobile terminals, smart phone, laptopmounted equipment (LME), universal serial bus (USB) dongles enabled formobile communications, a computer having mobile capabilities, a mobiledevice such as cellular phone, a laptop having laptop embedded equipment(LEE, such as a mobile broadband adapter), a tablet computer having amobile broadband adapter, a wearable device, a virtual reality (VR)device, a heads-up display (HUD) device, a smart car, a machine-typecommunication (MTC) device, and the like. User equipment UE 102 can alsocomprise IOT devices that communicate wirelessly.

In various embodiments, system 100 is or comprises a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. In example embodiments, a UE 102 can becommunicatively coupled to the wireless communication network via anetwork node 104. The network node (e.g., network node device) cancommunicate with user equipment (UE), thus providing connectivitybetween the UE and the wider cellular network. The UE 102 can sendtransmission type recommendation data to the network node 104. Thetransmission type recommendation data can comprise a recommendation totransmit data via a closed loop MIMO mode and/or a rank-1 precoder mode.

A network node can have a cabinet and other protected enclosures, anantenna mast, and multiple antennas for performing various transmissionoperations (e.g., MIMO operations). Network nodes can serve severalcells, also called sectors, depending on the configuration and type ofantenna. In example embodiments, the UE 102 can send and/or receivecommunication data via a wireless link to the network node 104. Thedashed arrow lines from the network node 104 to the UE 102 representdownlink (DL) communications and the solid arrow lines from the UE 102to the network nodes 104 represents an uplink (UL) communication.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. The one or morecommunication service provider networks 106 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, millimeter wave networks andthe like. For example, in at least one implementation, system 100 can beor include a large scale wireless communication network that spansvarious geographic areas. According to this implementation, the one ormore communication service provider networks 106 can be or include thewireless communication network and/or various additional devices andcomponents of the wireless communication network (e.g., additionalnetwork devices and cell, additional UEs, network server devices, etc.).The network node 104 can be connected to the one or more communicationservice provider networks 106 via one or more backhaul links 108. Forexample, the one or more backhaul links 108 can comprise wired linkcomponents, such as a T1/E1 phone line, a digital subscriber line (DSL)(e.g., either synchronous or asynchronous), an asymmetric DSL (ADSL), anoptical fiber backbone, a coaxial cable, and the like. The one or morebackhaul links 108 can also include wireless link components, such asbut not limited to, line-of-sight (LOS) or non-LOS links which caninclude terrestrial air-interfaces or deep space links (e.g., satellitecommunication links for navigation).

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and the network node104). While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000 etc.

For example, system 100 can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system 100 are particularlydescribed wherein the devices (e.g., the UEs 102 and the network device104) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi -carrier operation”, “multi -carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks are expected to fulfill the demand ofexponentially increasing data traffic and to allow people and machinesto enjoy gigabit data rates with virtually zero latency. Compared to 4G,5G supports more diverse traffic scenarios. For example, in addition tothe various types of data communication between conventional UEs (e.g.,phones, smartphones, tablets, PCs, televisions, Internet enabledtelevisions, etc.) supported by 4G networks, 5G networks can be employedto support data communication between smart cars in association withdriverless car environments, as well as machine type communications(MTCs). Considering the drastic different communication needs of thesedifferent traffic scenarios, the ability to dynamically configurewaveform parameters based on traffic scenarios while retaining thebenefits of multi carrier modulation schemes (e.g., OFDM and relatedschemes) can provide a significant contribution to the highspeed/capacity and low latency demands of 5G networks. With waveformsthat split the bandwidth into several sub-bands, different types ofservices can be accommodated in different sub-bands with the mostsuitable waveform and numerology, leading to an improved spectrumutilization for 5G networks.

To meet the demand for data centric applications, features of proposed5G networks may comprise: increased peak bit rate (e.g., 20 Gbps),larger data volume per unit area (e.g., high system spectralefficiency—for example about 3.5 times that of spectral efficiency oflong term evolution (LTE) systems), high capacity that allows moredevice connectivity both concurrently and instantaneously, lowerbattery/power consumption (which reduces energy and consumption costs),better connectivity regardless of the geographic region in which a useris located, a larger numbers of devices, lower infrastructuraldevelopment costs, and higher reliability of the communications. Thus,5G networks may allow for: data rates of several tens of megabits persecond should be supported for tens of thousands of users, 1 gigabit persecond to be offered simultaneously to tens of workers on the sameoffice floor, for example; several hundreds of thousands of simultaneousconnections to be supported for massive sensor deployments; improvedcoverage, enhanced signaling efficiency; reduced latency compared toLTE.

The upcoming 5G access network may utilize higher frequencies (e.g., >6GHz) to aid in increasing capacity. Currently, much of the millimeterwave (mmWave) spectrum, the band of spectrum between 30 GHz and 300 GHzis underutilized. The millimeter waves have shorter wavelengths thatrange from 10 millimeters to 1 millimeter, and these mmWave signalsexperience severe path loss, penetration loss, and fading. However, theshorter wavelength at mmWave frequencies also allows more antennas to bepacked in the same physical dimension, which allows for large-scalespatial multiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingcapacity of wireless systems. The use of multiple-input multiple-output(MIMO) techniques can improve mmWave communications, and has been widelyrecognized a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems, and are planned for use in 5G systems.

FIG. 2 illustrates a block diagram of an exemplary 5G networkarchitecture 200. For example, the network architecture 200 can comprisea core network 202 deploying a monolithic gNB 206 and/or a central unit(CU)-distributed unit (DU) split gNB 208 architecture, as part of a nextgeneration radio access network (NG-RAN) 204. Currently, the gNB 206 andgNB 208 can communicate using a Xn-C interface 220. The monolithic gNB206 comprises of user plane (UP) protocol functions such as service dataadaptation protocol (SDAP), packet data convergence protocol (PDCP),radio link control (RLC), medium access control (MAC), and physicallayer (PHY), and control plane (CP) functions such as radio resourcecontrol (RRC), PDCP, RLC, MAC and PHY (not shown). The gNB (CU-DU) 208comprises gNB (CU) 210 which can be further split into gNB-CU-CPcontaining the CU functions RRC/PDCP and multiple gNB-CU-Ups containinguser plane functions SDAP/PDCP. The gNB-DU 212 and gNB-DU 214 comprisesprotocol functions RLC/MAC/PHY. The gNB-DU 212 and gNB-DU 214 arecommunicatively connected to gNB-CU via F1 interface 222.

FIG. 3A illustrates an example of protocol functions for a gNB withCU-DU split architecture 300 according to various aspects andembodiments described herein. The CU-DU split architecture 300 cancomprise gNB-CU 302 and a gNB-DU 330. The gNB-CU 302 can comprise aCU-UP 310 and CU-CP 320. The CU-UP 310 comprises user plane protocolfunctions such as SDAP 312 and PDCP 314. The CU-CP 320 comprises controlplane protocol functions such as RRC 322 and PDCP 324. Correspondingly,the gNB-DU 330 comprises protocol functions such as RLC 332, MAC 334 andPHY 336. It should be noted that all the concepts discussed hereinrelated to the gNB with CU-DU architecture can also be applied to themonolithic gNB architecture. This architecture allows for carrieraggregation across different component carriers that can be supportedacross two different non-co-located gNBs or gNB-DUs.

FIG. 3B illustrates an example of CU-DU split architecture 350 accordingto various aspects and embodiments described herein. In the CU-DU splitarchitecture 350, a CU A 310A can communicate with a UE via inter-DUarchitecture, wherein the transmission can occur using DU A 330A and DUB 330B that belong to the same CU A 310A. In some embodiments, twodifferent non-co-located CUs (e.g., CU A 310A and CU B 310B) cancommunicate with UE B 340B using DUs from each respective CU (e.g.,inter-CU). For example, transmission to UE B 340B can occur from the CUA 310A using DUB 330B and the CU B 310B using DU C 330C.

In some embodiments, multi-TRP transmission can be utilized tocommunicate with the UE. For example, in a multi-TRP with a singledownlink control information (DCI) that provides UE with the necessaryinformation such as physical layer resource allocation, power controlcommands, HARQ information for both uplink and downlink, a common MAClayer may perform joint scheduling between 2 TRPs. This may require theMAC to be located at a central location with very low latency transportto multiple TRPs to allow the MAC to jointly schedule transmissionacross multiple TRPs. In another example, in a multi-TRP with multi-DCI,each TRP may be scheduled independently by the same or separate MACs.This case allows non-ideal transport between the non-co-located TRPs.Note that independent scheduling for each TRP requires coordinationacross separate MAC entities corresponding to TRPs. Especially withnon-ideal transport it is difficult to achieve such coordination in atime scale that still meets the transmission and signaling timelinesrequired by wireless specifications.

In some embodiments, inter-DU/inter-CU CA can be used to communicatewith the UE. Carrier aggregation typically assumes that a single MACfunction is scheduling multiple aggregated component carriers. However,when carrier aggregation is performed across component carriers thatoriginate from non-co-located TRPs, the performance of the systembecomes quite sensitive to the transport latency between the two TRPs orDUs. This is because in the case of CA, all the uplink channel stateinformation (CSI) reports and HARQ feedback corresponding to the smallcell (SCell) carrier is first sent by the UE to a personal cell (PCell)carrier and then must be relayed over to the SCell. Especially when thetransport between PCell and SCell is non-ideal there can be significantdegradation in throughput performance experienced by the user.

An example for inter-DU/inter-CU CA, is CA across FR1 and FR2 carriersbetween a macro site and small cell site. Currently, the only reasonablesolution for aggregating across macro and small cell sites for FR1 andFR2 respectively is to either use a cloud-RAN (CRAN) type of solutionwith ideal transport or to perform dual connectivity. CA-based solutionsfor such a scenario may have significant performance loss. BothCRAN-based solutions and DC-based solution have their own drawbacks. Forexample, CRAN-based solutions require very low latency high throughputtransport, which can be cost prohibitive, and DC-based solutions provideaggregation at a much higher PDCP layer so they are not as responsive todynamically changing channel conditions across different componentcarriers as a CA-based solution can be. Described herein a solution thatenables inter-DU and inter-CU coordination between MAC entities thatmake it possible to more easily implement use cases such as inter-siteCA and inter-site multi-TRP transmission.

In some embodiments, a new logical interface, which we call the X_(mac)interface, between peer MAC entities at non-co-located gNB-DUs(distributed unit and centralized unit (CU)) is utilized to enableinter-DU and inter-CU coordination between MAC entities that make itpossible to more easily implement use cases such as inter-site CA andinter-site multi-TRP transmission. This X_(mac) interface enablescommunication of control and user plane information between peer MACsfor coordination for inter-site CA or inter-site multi-TRP operation.The X_(mac) interface may consist of a control plane part, X_(mac)-C,and user plane part, X_(mac)-U. When configured to operate in inter-sitemode, the MAC at one of the DUs (for example, the DU that hosts thePCell), is designated as the primary MAC, and the MACs at other DUs ininter-site operation are designated as secondary MACs. In someembodiments, the MAC layer may be split into a higher MAC (MAC-H) andlower MAC (MAC-L), where the MAC-H at the primary is in control of theMAC-Ls residing at all the DUs corresponding to all the secondary MACs.Also, the X_(mac) interface may be used to enable inter-site CA orinter-site multi-TRP operation across multiple sites.

The advantage of the described solution are that direct MAC-to-MACenables coordination between peer DUs that are either under the same CUor under different CUs; enables inter-site CA without requiring acentralized MAC and very low latency high throughput transport betweenDUs; enables inter-site multi-TRP transmission with multi-DCI acrossnon-co-located DUs; and inter-site CA solutions via a MAC-MAC interfacecan be enabled across more than two sites because it is still a CA-basedsolution, so it requires the UEs to transmit only on a single PCelluplink.

FIG. 4A illustrates a block diagram of an example, non-limiting system400 that facilitates establishing a medium access control interface tocoordinate communication between distribution units in accordance withone or more embodiments described herein. The system 400 comprises agNB-DU A 430A and gNB-DU 430B, wherein the gNB-DU A comprises a RLC432A, MAC 434A and PHY 436A, and the gNB-DU B comprises a RLC 432B, MAC434B and PHY 436B. In some embodiments, a X_(mac) interface 422 thatfacilitates communication between two MAC layers (MAC 434A and MAC 434B)is provided. The interface 422 allows direct coordination MAC entitiesof non-co-located DUs. Such a MAC-MAC interface can carry controlsignalling for coordination between peer MAC entities, and also carryuser plane traffic from one MAC to another MAC. The X_(mac) interface422 is defined as a logical interface. Physically this interface may becarried in different ways between two the MACs, for example, via adirect fiber connection between DUs, or via a wireless connectionbetween DUs, or tunnelled through another interface.

In some embodiments, the MAC at one DU (e.g., 434A) is designated as theprimary MAC, while the MAC at the peer DU (e.g., 434B) is designated asthe secondary MAC. For example, in the case of inter-site CA, the MACassociated with the PCell carrier is designated as the primary MAC,while the MAC associated with a SCell carrier is designated as thesecondary MAC. In some embodiments, the primary MAC (e.g., 434A)controls of the secondary MAC (e.g., 434B) via the X_(mac) interface422.

In some embodiments, the X_(mac) interface 422 comprises two parts, acontrol plane (X_(mac)-C interface) and user plane (e.g., X_(mac)-Uinterface). The control plane part, X_(mac)-C, may use control planemessages with various information elements to allow exchange ofcoordination information between peer MAC entities. In the case ofmulti-TRP operation with multi-DCI, the inter-MAC coordinationinformation, may include UE-reported CSI and rank, spatial layers, DCIconfiguration, PDSCH configuration, HARQ processes, etc. In the case ofinter-site CA use case, the X_(mac)-C may relay CSI feedback and HARQfeedback information from the PCell MAC to SCell MAC. In addition, theX_(mac)-C could relay information from the SCell back to the PCellrelated to buffer status or throughput.

The user plane part, X_(mac)-U, may be used to transfer user plane datain the form of RLC PDUs from the primary MAC to a secondary MAC.Additionally, there may need to be some form of flow control between theprimary MAC and secondary MAC, in order to ensure proper flow of dataand to prevent wastage of resources on component carriers.

FIG. 4B illustrates a block diagram of an example, non-limiting system450 that facilitates establishing a medium access control interface tocoordinate communication between distribution units in accordance withone or more embodiments described herein. In some embodiments, the MAC434A FIG. 4A functions can be split between a higher MAC-H 470A and alower MAC-L 472A. At the MAC of the primary DU (e.g., gNB-DU A 430A),the MAC-H is fully instantiated. However, at the MACs for the secondary(e.g., gNB-DUs 430B through 430N), the MAC-H (e.g., 470B through 470N)is in passive mode. The MAC-L at each DU operates independently of otherMAC-Ls. On the primary side, the MAC-L simply communicates with theMAC-H above.

In some embodiments, the MAC-L is unaware of whether the MAC-H above itis in active mode or passive mode. When the MAC-H is in active mode, forexample, at the primary MAC (e.g., MAC-H 472A) at PCell DU, the MAC-L(e.g., MAC-L 472A) is directly controlled by the MAC-H 472A above it.However, when the MAC-H (e.g., MAC-H 470B through 470N) is in passivemode, for example, at the secondary MAC (gNB-DUs 430B through 430N), theMAC-L 472B through 472N are indirectly controlled by the MAC-H 470Aresiding at the primary MAC (gNB-DUs 430A). In this case, when thepassive MAC-H (e.g., 472B) at the secondary MAC receives control or userplane information from the active MAC-H (e.g., 472A) at the primary MAC(gNB-DUs 430A), and the passive MAC-H (e.g. 470B) simply translates thereceived information in order to pass down the required information tocontrol the MAC-L (e.g., 472B). This allows the MAC-L (e.g., 472B) to bedesigned to receive information from the MAC-H (e.g., 470B) above itwithout being aware of whether it is being controlled by the local MAC-H(e.g., 470A) or a remote MAC-H (e.g., 470B). The MAC-L (e.g., 472A) alsodoes not have to be aware of the X_(mac) interface. Such a frameworkallows highly flexible MAC configuration to individually operate eachbearer in either intra-site or inter-site mode.

In some embodiments, the functions residing at the MAC-H (e.g., 470A)may include upper level MAC/scheduler functions such as user selection,scheduling metric calculations, QoS considerations, flow control overX_(mac) interface etc. In such an embodiment the corresponding functionsresiding at the MAC-L (e.g., 470B) may include lower MAC/schedulerfunctions such as resource allocation, HARQ processing, etc. The variousembodiments herein do not preclude other embodiments with other ways ofsplitting functions between MAC-H and MAC-L.

In some embodiments, the procedure that is used by the CU-CP to set upaggregation with a new carrier is called RRC reconfiguration. When theCU-CP triggers the RRC reconfiguration to add a new carrier (calledsecondary cell or SCell) belonging to a non-co-located DU for a UE, thiscould trigger the establishment of the X_(mac) interface between the twoDUs for that particular UE. In general, as long as there is at least oneUE operating in inter-site TRP or inter-site CA mode between two DUs,there would be an established X_(mac) interface between those two DUs.

FIG. 5 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein. In someexamples, flow diagram 500 can be implemented by operating environment900 described below. It can be appreciated that the operations of flowdiagram 500 can be implemented in a different order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 902) is provided, the device or system comprising one ormore processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 5.

Operation 502 depicts monitoring, by a device comprising a processor,communication between a network node device and a communication device,wherein information is communicated by utilizing a first distributionunit node device comprising a first medium access control layercomponent of the network node device. Operation 504 depicts receiving,by the device, a condition, wherein the condition indicates whether toadd a second distribution unit node device comprising a second mediumaccess control layer component to be utilized by the communicationdevice (e.g., when the CU-CP triggers the RRC reconfiguration to add anew carrier belonging to a non-co-located DU for a UE, this couldtrigger the establishment of the X_(mac) interface between the two DUsfor that particular UE). Operation 506 depicts, if the conditionindicates to add a second distribution unit node device, performoperation 508. Otherwise, continue monitoring. Operation 508 depicts inresponse to determining that the condition indicates addition of thesecond distribution unit node device, facilitating, by the device,establishing a connection between the first medium access control layercomponent of the first distribution unit node device and the secondmedium access control layer component of the second distribution unitnode device using a medium access control interface. Operation 510depicts initiating, by the device, communication of control planeinformation and user plane information between the first medium accesscontrol layer component and the second medium access control layercomponent using the medium access control interface.

FIG. 6 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein. In someexamples, flow diagram 600 can be implemented by operating environment900 described below. It can be appreciated that the operations of flowdiagram 600 can be implemented in a different order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 902) is provided, the device or system comprising one ormore processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 6.

Operation 602 depicts monitoring, by a device comprising a processor,communication between a network node device and a communication device,wherein information is communicated by utilizing a first distributionunit node device comprising a first medium access control layercomponent of the network node device. Operation 604 depicts receiving,by the device, a condition, wherein the condition indicates whether toadd a second distribution unit node device comprising a second mediumaccess control layer component to be utilized by the communicationdevice (e.g., when the CU-CP triggers the RRC reconfiguration to add anew carrier belonging to a non-co-located DU for a UE, this couldtrigger the establishment of the X_(mac) interface between the two DUsfor that particular UE). Operation 606 depicts, if the conditionindicates to add a second distribution unit node device, performoperation 608. Otherwise, continue monitoring. Operation 608 depicts inresponse to determining that the condition indicates addition of thesecond distribution unit node device, facilitating, by the device,establishing a connection between the first medium access control layercomponent of the first distribution unit node device and the secondmedium access control layer component of the second distribution unitnode device using a medium access control interface. Operation 610depicts initiating, by the device, communication of control planeinformation and user plane information between the first medium accesscontrol layer component and the second medium access control layercomponent using the medium access control interface. Operation 612depicts dividing, by the device, operations of the first medium accesscontrol layer component by utilizing a first higher medium accesscontrol layer component and a first lower medium access control layercomponent.

FIG. 7 depicts a diagram of an example, non-limiting computerimplemented method that facilitates establishing a medium access controlinterface to coordinate communication between distribution units inaccordance with one or more embodiments described herein. In someexamples, flow diagram 700 can be implemented by operating environment900 described below. It can be appreciated that the operations of flowdiagram 700 can be implemented in a different order than is depicted.

In non-limiting example embodiments, a computing device (or system)(e.g., computer 902) is provided, the device or system comprising one ormore processors and one or more memories that stores executableinstructions that, when executed by the one or more processors, canfacilitate performance of the operations as described herein, includingthe non-limiting methods as illustrated in the flow diagrams of FIG. 7.

Operation 702 depicts monitoring, by a device comprising a processor,communication between a network node device and a communication device,wherein information is communicated by utilizing a first distributionunit node device comprising a first medium access control layercomponent of the network node device. Operation 704 depicts receiving,by the device, a condition, wherein the condition indicates whether toadd a second distribution unit node device comprising a second mediumaccess control layer component to be utilized by the communicationdevice (e.g., when the CU-CP triggers the RRC reconfiguration to add anew carrier belonging to a non-co-located DU for a UE, this couldtrigger the establishment of the X_(mac) interface between the two DUsfor that particular UE). Operation 706 depicts, if the conditionindicates to add a second distribution unit node device, performoperation 708. Otherwise, continue monitoring. Operation 708 depicts inresponse to determining that the condition indicates addition of thesecond distribution unit node device, facilitating, by the device,establishing a connection between the first medium access control layercomponent of the first distribution unit node device and the secondmedium access control layer component of the second distribution unitnode device using a medium access control interface. Operation 710depicts initiating, by the device, communication of control planeinformation and user plane information between the first medium accesscontrol layer component and the second medium access control layercomponent using the medium access control interface. Operation 712depicts dividing, by the device, operations of the first medium accesscontrol layer component by utilizing a first higher medium accesscontrol layer component and a first lower medium access control layercomponent. Operation 714 depicts designating, by the device, the firsthigher medium access control layer component as a first primary mediumaccess control layer component, wherein the first primary medium accesscontrol layer component controls the first lower medium access controllayer component.

Referring now to FIG. 8, illustrated is an example block diagram of anexample mobile handset 800 operable to engage in a system architecturethat facilitates wireless communications according to one or moreembodiments described herein. Although a mobile handset is illustratedherein, it will be understood that other devices can be a mobile device,and that the mobile handset is merely illustrated to provide context forthe embodiments of the various embodiments described herein. Thefollowing discussion is intended to provide a brief, general descriptionof an example of a suitable environment in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset includes a processor 802 for controlling and processing allonboard operations and functions. A memory 804 interfaces to theprocessor 802 for storage of data and one or more applications 806(e.g., a video player software, user feedback component software, etc.).Other applications can include voice recognition of predetermined voicecommands that facilitate initiation of the user feedback signals. Theapplications 806 can be stored in the memory 804 and/or in a firmware808 and executed by the processor 802 from either or both the memory 804or/and the firmware 808. The firmware 808 can also store startup codefor execution in initializing the handset 800. A communicationscomponent 810 interfaces to the processor 802 to facilitatewired/wireless communication with external systems, e.g., cellularnetworks, VoIP networks, and so on. Here, the communications component810 can also include a suitable cellular transceiver 811 (e.g., a GSMtransceiver) and/or an unlicensed transceiver 813 (e.g., Wi-Fi, WiMax)for corresponding signal communications. The handset 800 can be a devicesuch as a cellular telephone, a PDA with mobile communicationscapabilities, and messaging-centric devices. The communicationscomponent 810 also facilitates communications reception from terrestrialradio networks (e.g., broadcast), digital satellite radio networks, andInternet-based radio services networks.

The handset 800 includes a display 812 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 812 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 812 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface814 is provided in communication with the processor 802 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE 894)through a hardwire connection, and other serial input devices (e.g., akeyboard, keypad, and mouse). This can support updating andtroubleshooting the handset 800, for example. Audio capabilities areprovided with an audio I/O component 816, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 816 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 800 can include a slot interface 818 for accommodating a SIC(Subscriber Identity Component) in the form factor of a card SubscriberIdentity Module (SIM) or universal SIM 820, and interfacing the SIM card820 with the processor 802. However, it is to be appreciated that theSIM card 820 can be manufactured into the handset 800, and updated bydownloading data and software.

The handset 800 can process IP data traffic through the communicationscomponent 810 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 800 and IP-based multimediacontent can be received in either an encoded or decoded format.

A video processing component 822 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 822can aid in facilitating the generation, editing, and sharing of videoquotes. The handset 800 also includes a power source 824 in the form ofbatteries and/or an AC power subsystem, which power source 824 caninterface to an external power system or charging equipment (not shown)by a power I/O component 826.

The handset 800 can also include a video component 830 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 830 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 832 facilitates geographically locating the handset 800. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 834facilitates the user initiating the quality feedback signal. The userinput component 834 can also facilitate the generation, editing andsharing of video quotes. The user input component 834 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touchscreen, for example.

Referring again to the applications 806, a hysteresis component 836facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 838 can be provided that facilitatestriggering of the hysteresis component 836 when the Wi-Fi transceiver813 detects the beacon of the access point. A SIP client 840 enables thehandset 800 to support SIP protocols and register the subscriber withthe SIP registrar server. The applications 806 can also include a client842 that provides at least the capability of discovery, play and storeof multimedia content, for example, music.

The handset 800, as indicated above related to the communicationscomponent 810, includes an indoor network radio transceiver 813 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE-802.11, for the dual-mode GSM handset 800. The handset 800 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 9, illustrated is an example block diagram of anexample computer 900 operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein. The computer 900 can provide networking andcommunication capabilities between a wired or wireless communicationnetwork and a server and/or communication device.

In order to provide additional context for various embodiments describedherein, FIG. 9 and the following discussion are intended to provide abrief, general description of a suitable computing environment 900 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 9, the example environment 900 forimplementing various embodiments of the aspects described hereinincludes a computer 902, the computer 902 including a processing unit904, a system memory 906 and a system bus 908. The system bus 908couples system components including, but not limited to, the systemmemory 906 to the processing unit 904. The processing unit 904 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 904.

The system bus 908 can be any of several types of bus structure that canfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906 includesROM 910 and RAM 912. A basic input/output system (BIOS) can be stored ina non-volatile memory such as ROM, erasable programmable read onlymemory (EPROM), EEPROM, which BIOS contains the basic routines that helpto transfer information between elements within the computer 902, suchas during startup. The RAM 912 can also include a high-speed RAM such asstatic RAM for caching data.

The computer 902 further includes an internal hard disk drive (HDD) 914(e.g., EIDE, SATA), one or more external storage devices 916 (e.g., amagnetic floppy disk drive (FDD) 916, a memory stick or flash drivereader, a memory card reader, etc.) and an optical disk drive 920 (e.g.,which can read or write from a CD-ROM disc, a DVD, a BD, etc.). Whilethe internal HDD 914 is illustrated as located within the computer 902,the internal HDD 914 can also be configured for external use in asuitable chassis (not shown). Additionally, while not shown inenvironment 900, a solid state drive (SSD) could be used in addition to,or in place of, an HDD 914. The HDD 914, external storage device(s) 916and optical disk drive 920 can be connected to the system bus 908 by anHDD interface 924, an external storage interface 926 and an opticaldrive interface 928, respectively. The interface 924 for external driveimplementations can include at least one or both of Universal Serial Bus(USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394interface technologies. Other external drive connection technologies arewithin contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 902, the drives and storagemedia accommodate the storage of any data in a suitable digital format.Although the description of computer-readable storage media above refersto respective types of storage devices, it should be appreciated bythose skilled in the art that other types of storage media which arereadable by a computer, whether presently existing or developed in thefuture, could also be used in the example operating environment, andfurther, that any such storage media can contain computer-executableinstructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 912,including an operating system 930, one or more application programs 932,other program modules 934 and program data 936. All or portions of theoperating system, applications, modules, and/or data can also be cachedin the RAM 912. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 902 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 930, and the emulated hardwarecan optionally be different from the hardware illustrated in FIG. 9. Insuch an embodiment, operating system 930 can comprise one virtualmachine (VM) of multiple VMs hosted at computer 902. Furthermore,operating system 930 can provide runtime environments, such as the Javaruntime environment or the .NET framework, for applications 932. Runtimeenvironments are consistent execution environments that allowapplications 932 to run on any operating system that includes theruntime environment. Similarly, operating system 930 can supportcontainers, and applications 932 can be in the form of containers, whichare lightweight, standalone, executable packages of software thatinclude, e.g., code, runtime, system tools, system libraries andsettings for an application.

Further, computer 902 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 902, e.g., applied at the application execution level or at theoperating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 902 throughone or more wired/wireless input devices, e.g., a keyboard 938, a touchscreen 940, and a pointing device, such as a mouse 942. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 904 through an input deviceinterface 944 that can be coupled to the system bus 908, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 946 or other type of display device can be also connected tothe system bus 908 via an interface, such as a video adapter 948. Inaddition to the monitor 946, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 902 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 950. The remotecomputer(s) 950 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device 952is illustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 954 and/or larger networks,e.g., a wide area network (WAN) 956. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which canconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 902 can beconnected to the local network 954 through a wired and/or wirelesscommunication network interface or adapter 958. The adapter 958 canfacilitate wired or wireless communication to the LAN 954, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 958 in a wireless mode.

When used in a WAN networking environment, the computer 902 can includea modem 960 or can be connected to a communications server on the WAN956 via other means for establishing communications over the WAN 956,such as by way of the Internet. The modem 960, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 908 via the input device interface 944. In a networked environment,program modules depicted relative to the computer 902 or portionsthereof, can be stored in the remote memory/storage device 952. It willbe appreciated that the network connections shown are example and othermeans of establishing a communications link between the computers can beused.

When used in either a LAN or WAN networking environment, the computer902 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 916 asdescribed above. Generally, a connection between the computer 902 and acloud storage system can be established over a LAN 954 or WAN 956 e.g.,by the adapter 958 or modem 960, respectively. Upon connecting thecomputer 902 to an associated cloud storage system, the external storageinterface 926 can, with the aid of the adapter 958 and/or modem 960,manage storage provided by the cloud storage system as it would othertypes of external storage. For instance, the external storage interface926 can be configured to provide access to cloud storage sources as ifthose sources were physically connected to the computer 902.

The computer 902 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” “relay device,”“node,” “point,” and the like, are utilized interchangeably in thesubject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream to and froma set of subscriber stations or provider enabled devices. Data andsignaling streams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

While the various embodiments are susceptible to various modificationsand alternative constructions, certain illustrated implementationsthereof are shown in the drawings and have been described above indetail. It should be understood, however, that there is no intention tolimit the various embodiments to the specific forms disclosed, but onthe contrary, the intention is to cover all modifications, alternativeconstructions, and equivalents falling within the spirit and scope ofthe various embodiments.

In addition to the various implementations described herein, it is to beunderstood that other similar implementations can be used ormodifications and additions can be made to the describedimplementation(s) for performing the same or equivalent function of thecorresponding implementation(s) without deviating therefrom. Stillfurther, multiple processing chips or multiple devices can share theperformance of one or more functions described herein, and similarly,storage can be affected across a plurality of devices. Accordingly, thedescription is not to be limited to any single implementation, butrather is to be construed in breadth, spirit and scope in accordancewith the appended claims.

What is claimed is:
 1. A method, comprising: facilitating, by a firstdistribution unit node device comprising a processor, establishing aconnection between a first medium access control layer component of thefirst distribution unit node device and a second medium access controllayer component of a second distribution unit node device; andfacilitating, by the first distribution unit node device, controlling,via the first medium access control layer component, the second mediumaccess control layer component.
 2. The method of claim 1, whereinfacilitating the controlling comprises communicating control planemessages between the first medium access control layer component and thesecond medium access control layer component.
 3. The method of claim 1,wherein facilitating the controlling comprises communicating user planemessages between the first medium access control layer component and thesecond medium access control layer component.
 4. The method of claim 1,wherein the first distribution unit node device is not co-located withthe second distribution unit node device.
 5. The method of claim 1,wherein facilitating the controlling comprises, in response to the firstmedium access control layer component operating in an active mode,directly controlling the second medium access control layer component.6. The method of claim 1, wherein facilitating the controllingcomprises, in response to the first medium access control layercomponent operating in a passive mode, indirectly controlling the secondmedium access control layer component.
 7. The method of claim 1, whereinindirectly controlling the second medium access control layer componentcomprises passing through messages from a third second medium accesscontrol layer component of a third distribution unit node device to thesecond medium access control layer component.
 8. A first distributionunit node device, comprising: a processor; and a memory that storesexecutable instructions that, when executed by the processor, facilitateperformance of operations, comprising: instantiating a connectionbetween a first medium access control layer component of the firstdistribution unit node device and a second medium access control layercomponent of a second distribution unit node device; and controlling,via the first medium access control layer component, the second mediumaccess control layer component.
 9. The first distribution unit nodedevice of claim 8, wherein the controlling comprises communicatingcontrol plane information between the first medium access control layercomponent and the second medium access control layer component.
 10. Thefirst distribution unit node device of claim 8, wherein the controllingcomprises communicating user plane information between the first mediumaccess control layer component and the second medium access controllayer component.
 11. The first distribution unit node device of claim 8,wherein the first distribution unit node device is not co-located withthe second distribution unit node device.
 12. The first distributionunit node device of claim 8, wherein the controlling comprises, inresponse to the first medium access control layer component operating inan active mode, directly controlling the second medium access controllayer component.
 13. The first distribution unit node device of claim 8,wherein the controlling comprises, in response to the first mediumaccess control layer component operating in a passive mode, indirectlycontrolling the second medium access control layer component.
 14. Thefirst distribution unit node device of claim 8, wherein indirectlycontrolling the second medium access control layer component comprisespassing through information from a third second medium access controllayer component of a third distribution unit node device to the secondmedium access control layer component.
 15. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor of a first distribution unit node device,facilitate performance of operations, comprising: communicativelyconnecting a first medium access control layer component of the firstdistribution unit node device and a second medium access control layercomponent of a second distribution unit node device; and managing, viathe first medium access control layer component, the second mediumaccess control layer component.
 16. The non-transitory machine-readablemedium of claim 15, wherein the managing comprises communicating controlplane information between the first medium access control layercomponent and the second medium access control layer component.
 17. Thenon-transitory machine-readable medium of claim 15, wherein the managingcomprises communicating user plane information between the first mediumaccess control layer component and the second medium access controllayer component.
 18. The non-transitory machine-readable medium of claim15, wherein the first distribution unit node device is located remotefrom the second distribution unit node device.
 19. The non-transitorymachine-readable medium of claim 15, wherein the managing comprises, inresponse to the first medium access control layer component operating inan active mode, directly managing the second medium access control layercomponent.
 20. The non-transitory machine-readable medium of claim 15,wherein the managing comprises, in response to the first medium accesscontrol layer component operating in a passive mode, indirectly managingthe second medium access control layer component.